Skip to content

Fix < 1.20.0 version physical restore error #1972

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix < 1.20.0 version physical restore error #1972

wants to merge 2 commits into from
+9 −3

Conversation

cccfs
Copy link

@cccfs cccfs commented Jun 19, 2025 •
edited by pull-request-badge bot
Loading

CHANGE DESCRIPTION

Problem:
Using the latest version 0.20.1 and defining crVersion 1.15.0 to deploy MongoDB 4.4.24x replica set, there are compatibility issues with panic and pbm version configurations when running physical restore

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Short explanation of the solution we are providing with this PR.

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?
  • Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Are all needed new/changed options added to the Helm Chart?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported MongoDB version?
  • Does the change support oldest and newest supported Kubernetes version?

@pull-request-size pull-request-size bot added the size/S 10-29 lines label Jun 19, 2025
@CLAassistant
Copy link

CLAassistant commented Jun 19, 2025 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@JNKPercona
Copy link
Collaborator

Test name Status
arbiter passed
balancer passed
cross-site-sharded passed
custom-replset-name passed
custom-tls passed
custom-users-roles passed
custom-users-roles-sharded passed
data-at-rest-encryption passed
data-sharded passed
demand-backup passed
demand-backup-eks-credentials-irsa passed
demand-backup-fs passed
demand-backup-incremental passed
demand-backup-incremental-sharded passed
demand-backup-physical-parallel passed
demand-backup-physical-aws passed
demand-backup-physical-azure passed
demand-backup-physical-gcp passed
demand-backup-physical-minio passed
demand-backup-physical-sharded-parallel passed
demand-backup-physical-sharded-aws passed
demand-backup-physical-sharded-azure passed
demand-backup-physical-sharded-gcp passed
demand-backup-physical-sharded-minio passed
demand-backup-sharded passed
expose-sharded passed
finalizer passed
ignore-labels-annotations passed
init-deploy passed
ldap passed
ldap-tls passed
limits passed
liveness passed
mongod-major-upgrade passed
mongod-major-upgrade-sharded passed
monitoring-2-0 passed
monitoring-pmm3 passed
multi-cluster-service passed
multi-storage passed
non-voting-and-hidden passed
one-pod passed
operator-self-healing-chaos passed
pitr passed
pitr-physical passed
pitr-sharded passed
pitr-physical-backup-source passed
preinit-updates passed
pvc-resize passed
recover-no-primary passed
replset-overrides passed
rs-shard-migration passed
scaling passed
scheduled-backup passed
security-context passed
self-healing-chaos passed
service-per-pod passed
serviceless-external-nodes passed
smart-update passed
split-horizon passed
stable-resource-version passed
storage passed
tls-issue-cert-manager passed
upgrade passed
upgrade-consistency passed
upgrade-consistency-sharded-tls passed
upgrade-sharded passed
users passed
version-service passed
We run 68 out of 68

commit: 416c6a9
image: perconalab/percona-server-mongodb-operator:PR-1972-416c6a9a

@hors hors added the community label Jun 22, 2025
@egegunes
Copy link
Contributor

@cccfs may i ask why do you use crVersion: 1.15.0 with the latest version? is it because of MongoDB version? because neither operator v1.15 nor MongoDB v4.4 is supported any more. v4.4 support is dropped in v1.16.0

@cccfs
Copy link
Author

cccfs commented Jul 1, 2025

@cccfs may i ask why do you use crVersion: 1.15.0 with the latest version? is it because of MongoDB version? because neither operator v1.15 nor MongoDB v4.4 is supported any more. v4.4 support is dropped in v1.16.0

I have an instance of MongoDB 4.4 hosted on a public cloud and expect to migrate it to an operator managed MongoDB. To ensure migration to the same version, I specified crVersion: 1.15.0 to start the replica set of MongoDB 4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hors hors Awaiting requested review from hors hors is a code owner

@egegunes egegunes Awaiting requested review from egegunes egegunes is a code owner

@pooknull pooknull Awaiting requested review from pooknull pooknull is a code owner

@nmarukovich nmarukovich Awaiting requested review from nmarukovich nmarukovich is a code owner

@gkech gkech Awaiting requested review from gkech gkech is a code owner

At least 2 approving reviews are required to merge this pull request.

Assignees

@egegunes egegunes

Labels
community size/S 10-29 lines
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@cccfs @CLAassistant @JNKPercona @egegunes @hors